chore(deps-dev): bump the semantic-release group across 1 directory with 2 updates #544
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
…ith 2 updates Bumps the semantic-release group with 2 updates in the / directory: [@semantic-release/github](https://github.com/semantic-release/github) and [semantic-release](https://github.com/semantic-release/semantic-release). Updates `@semantic-release/github` from 10.3.2 to 10.3.5 - [Release notes](https://github.com/semantic-release/github/releases) - [Commits](semantic-release/github@v10.3.2...v10.3.5) Updates `semantic-release` from 24.1.0 to 24.1.1 - [Release notes](https://github.com/semantic-release/semantic-release/releases) - [Commits](semantic-release/semantic-release@v24.1.0...v24.1.1) --- updated-dependencies: - dependency-name: "@semantic-release/github" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: semantic-release - dependency-name: semantic-release dependency-type: direct:development update-type: version-update:semver-patch dependency-group: semantic-release ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
|
Looks like these dependencies are no longer updatable, so this is no longer needed. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/semantic-release-394cce669b
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps the semantic-release group with 2 updates in the / directory: @semantic-release/github and semantic-release.
Updates
@semantic-release/githubfrom 10.3.2 to 10.3.5Release notes
Sourced from
@semantic-release/github's releases.Commits
7fb46a3fix: replacesearchAPIusage withGraphQLinfindSRIssueutil (#907)e57dc0cci(action): update actions/setup-node action to v4.0.4 (#929)2cc8f1achore(deps): update dependency publint to v0.2.11 (#928)59cb02cchore(deps): lock file maintenance (#927)efe9f49fix(glob-assets): remove unnecessary option when invokingglobby()(#924)9ceb494chore(deps): update dependency npm-run-all2 to v6.2.3 (#926)10dfabcchore(deps): update dependency sinon to v19.0.2 (#923)ce2a68echore(deps): update dependency sinon to v19.0.1 (#922)c486225chore(deps): update dependency sinon to v19 (#921)7981b08chore(deps): update dependency semantic-release to v24.1.1 (#919)Updates
semantic-releasefrom 24.1.0 to 24.1.1Release notes
Sourced from semantic-release's releases.
Commits
ab10ac1fix(deps): update dependency hosted-git-info to v8 (#3436)da5f8bechore(deps): update dependency sinon to v18.0.1 (#3440)da38617chore(deps): update dependency micromatch to v4.0.8 [security] (#3433)66ac996ci(action): update actions/upload-artifact action to v4.4.0 (#3434)1d8d7afchore(deps): update npm to v10.8.3 (#3432)01f95fdchore(deps): update dependency nock to v13.5.5 (#3428)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions